System and method for regulating electronic messages

ABSTRACT

A system for regulating e-mail comprises a database of information profiling legitimate e-mail usage. When an e-mail is received at the system, it is scrutinized relative to the information in the database. If the e-mail is found to be legitimate based upon this evaluation, it is delivered to the intended recipient. If, however, the e-mail appears on the basis of the evaluation to be the last in a series of illegitimate e-mails or otherwise has characteristics inconsistent with the profile of legitimate e-mail usage, the e-mail may not be delivered and the postmaster and administrator at the source of the e-mail is contacted.

This application is a divisional of application Ser. No. 11/190,326, filed on Jul. 27, 2005, and entitled System and Method for Regulating Electronic Messages, which is a continuation of application Ser. No. 09/888,719, filed on Jun. 25, 2001, now U.S. Pat. No. 6,957,259 and entitled System and method for regulating emails by maintaining, updating and comparing the profile information for the email source to the target email statistics.

FIELD OF THE INVENTION

The present invention relates generally to electronic messaging systems such as, for example, e-mail and instant messaging, and more particularly, to systems and methods for intelligently regulating such electronic messaging systems.

BACKGROUND OF THE INVENTION

Over the past fifteen years, the use of electronic messaging systems such as e-mail and instant messaging has experienced tremendous growth. People regularly send and receive e-mails and instant messages at all times of the day from work, from home, and even from mobile devices. Indeed, for many people, e-mail and instant messaging has become a primary means of communication.

While e-mail, instant messaging, and other such electronic messaging systems represent great technologies and have enhanced communication in our society, they do not come without costs. As an example, e-mail users spend significant amounts of time reviewing and replying to the numerous e-mails that they receive daily. This task has been made more cumbersome and time consuming by the large quantities of junk e-mail, or SPAM, that continuously flows into e-mail in-boxes. E-mail users must sort this SPAM in order to get to the e-mail that he or she desires to view. Instant messaging users are presented with similar problems in discerning from whom to receive messages.

The dramatic rise in e-mail and instant messaging usage has come at a cost to the organizations that maintain computer networks as well. In order to service the growing electronic messaging traffic, Internet service providers (ISP's) and corporate computer departments have needed to continuously upgrade their systems. Furthermore, additional personnel are required to run these systems and must be routinely trained on the new systems. Frequently, despite the best efforts of ISP's and corporate computer departments, the growth in demand for electronic messaging services outpaces the added capacity provided by system upgrades.

Applicant has recognized that requiring e-mail users to sift through ever increasing amounts of e-mail, much of which is junk e-mail, and relying upon ISP's and corporate computer departments to continuously upgrade their equipment to service the electronic messaging, is a less than optimal situation. Applicant has recognized that there exists a need to intelligently regulate the flow of e-mail and instant messages, particularly that which is commercial in nature. Indeed, systems and methods are needed to monitor the types and amounts of electronic messages that are being received and to regulate those electronic messages depending upon the source and characteristics of the messages. It would be a significant improvement in the art to provide systems and methods for recognizing junk messages and limiting the amount that is received in a given period. Such an improvement would reduce the amount of SPAM received by users and would preserve scarce system resources for legitimate messages.

SUMMARY OF THE INVENTION

Briefly, the present invention meets these and other needs in the art.

Generally, the invention relates to systems and methods for intelligently regulating electronic messages. A system in accordance with the invention comprises an electronic message server with access to a database of information profiling legitimate electronic message usage. When an electronic message is received at the electronic message server, it is scrutinized relative to the information in the database. If the electronic message is found to be legitimate based upon this evaluation, it is delivered to the intended recipient. If, however, the electronic message appears on the basis of the evaluation to be the last in a series of illegitimate usage or otherwise has characteristics inconsistent with the profile of legitimate electronic message usage, the electronic message may not be delivered and the postmaster or administrator at the site from which the electronic message originated is contacted.

According to an aspect of the invention, the administrator or postmaster may register sources from which he or she anticipates receiving electronic messages. Electronic messages received from registered sources may be evaluated under different criteria than those received from unregistered sources. During the registration process, the postmaster may define a profile for the registered source defining the amounts and types of e-mails that are acceptable from the particular source. The list of registered sites is stored in a database along with the profile data for those registered sources.

A database in accordance with an aspect of the invention stores data that is used in evaluating electronic messages. The database comprises data defining acceptable electronic message usages from both registered and unregistered sources.

With respect to unregistered sources, the database comprises a list of categories of sources from which electronic messages might be received. These categories are referred to herein as “electronic message source categories.” Typical electronic message source categories might include, for example, the following: large ISP—designating ISP's servicing a large number of users; medium ISP—designating ISP's servicing a medium number of users; small ISP—designating ISP's servicing a small number of users; .gov—designating sources in the .gov domain; .edu—designating sources in the .edu domain; and .com—designating sources in the .com domain. Of course, other electronic message source categories may be used depending upon the type of electronic messages that it is desired to regulate.

The database further comprises a set of target statistics for each of the electronic message source categories. For example, the target statistics might include a maximum electronic message volume that may be received in a prescribed period of time from a source in a particular source category. The database may prescribe, for example, that a maximum of 200,000 e-mails may be received and processed from a source that is classified in the “.edu” source category. As explained in further detail below, the category statistics operate as benchmarks for the electronic message sources that fall within the particular category.

A set of target electronic message profiles is also maintained in the database for each electronic message source category. The target electronic message profiles identify target characteristics for electronic messages that are received from a source in a particular source category. For example, the target electronic message profile for a particular source category might identify the maximum size for an e-mail, the types of attachments that might be included with the e-mail, and the maximum number of “hops” that the e-mail may have taken prior to arriving at the electronic message server. These characteristics are used as benchmarks to identify irregular electronic message activities.

The database further comprises a set of statistics for each electronic message source. The statistics are continuously updated to reflect each electronic message that is received from a particular source. For example, each time an e-mail or an instant message is received in the system from a particular source such as, for example, www.bellsouth.com, the statistic holding the counter of e-mails or instant messages received from that particular site is incremented.

For each source that has been registered by the postmaster, a profile is established in the database identifying target statistics for each registered source and the types of electronic messages that are expected to be received from the source. The profile data for a registered source may include much of the same data that is collected for unregistered sites including the maximum size for an e-mail, the types of attachments that might be included with the e-mail, and the maximum number of “hops” that the e-mail may have taken prior to arriving at the electronic message server. The profile for a registered source might also identify whether the source has agreed to pay for certain services such as payment for the delivery of e-mail or the creation of e-mail usage reports.

An electronic message server in accordance with the invention implements methods using the above-described database to intelligently regulate the flow of electronic messages. According to a method in accordance with the invention, upon receipt of an electronic message, the source of the electronic message is identified and the statistics that are maintained for the electronic message source are updated to reflect the arrival of the new electronic message. For example, if an e-mail or instant message is received from smith@bellsouth.com, the statistic in the database identifying the number of e-mails or instant messages from bellsouth.com and the range of IP addresses that are associated with bellsouth.com are incremented.

Those skilled in the art will recognize that an electronic message that has been forwarded numerous times may have multiple domains or “sources” listed in its header. A single electronic message may be said to have “originated” from more than one source. Therefore, according to an aspect of the invention, for purposes of regulating messages an electronic message may be designated as originating from more than one source. For example, a single electronic message may be said to have originated from the first or the last “hop” identified in the header information. An electronic message that is designated as having originated from more than one domain is evaluated as described below twice, once for each of the two sources.

After the source of an electronic message has been identified, it is determined whether the source is registered or not. If so, the electronic message is evaluated relative to the profile data stored for the particular registered source.

If the electronic message was received from an un-registered source, the source category corresponding to the un-registered source is identified. With respect to the example e-mail or instant message from smith@bellsouth.com, the “.com” source category is identified. The statistics for the source of the e-mail or instant message, which have been updated to reflect receipt of the e-mail or instant message, are compared to the target statistics for the particular category. If the statistics for the source fail to comply with the benchmark target statistics, the sender and/or postmaster of the source from which the e-mail or instant message is received is automatically notified of such if it is a registered source. For example, if the volume of e-mail received from the source bellsouth.com exceeds the target volume, which may be indicative that SPAM is originating from bellsouth.com, an e-mail is sent to the sender and/or postmaster at www.bellsouth.com. The e-mail might indicate, for example that the amount of e-mail originating from the site has reached an unacceptable level along with a request to either reduce the volume of e-mail being forwarded or to contact the postmaster at the destination site. The postmaster of the e-mail system at bellsouth.com can investigate the cause for the excessive e-mail activity and if it turns out to be legitimate and was not a one-time occurrence, may interact with the postmaster at the recipient to negotiate accepting a larger volume of e-mail.

An electronic message server in accordance with the invention also operates to regulate the flow of electronic messages based upon a comparison of the electronic messages to a profile of acceptable electronic message characteristics. Accordingly, when an electronic message is received, and after it's source and source category have been identified as explained above, the profile for an acceptable electronic message from the particular source criteria are retrieved. If the electronic message fails to fall within the profile for the source category, it may be indicative of a virus or possibly SPAM, in which case, the electronic message is not delivered to the intended recipient but instead is returned to the sender and/or the postmaster of the site from which the electronic message originated.

If the electronic message satisfies the profile, it is further evaluated against a list of known viruses. If a virus is detected, the message is not delivered and the postmaster is notified. If, however, no virus is detected, the electronic message is delivered to the intended recipient.

Additional aspects of the invention are described in detail below.

BRIEF DESCRIPTION OF THE DRAWINGS

Other features of the invention will be further apparent from the following detailed description of presently preferred exemplary embodiments of the invention taken in conjunction with the accompanying drawings, of which:

FIG. 1 is a high level diagram of a network for transmitting electronic messages;

FIG. 2 is a block diagram of a computing system suitable for use in an embodiment of the present invention;

FIG. 3 is a diagram illustrating the functional components of a server computer or cluster of server computers for use in an embodiment of the present invention;

FIG. 4 is a diagram representing data entities stored in a database system in accordance with an embodiment of the present invention;

FIGS. 5A, 5B, and 5C are flow diagrams of a method in accordance with the invention for managing electronic messages; and

FIG. 6 is a flow diagram of a process for registering a source with the system.

DETAILED DESCRIPTION OF THE INVENTION

A system and method with the above-mentioned beneficial features in accordance with a presently preferred exemplary embodiment of the invention will be described below with reference to FIGS. 1-6. It will be appreciated by those of ordinary skill in the art that the description given herein with respect to those figures is for exemplary purposes only and is not intended in any way to limit the scope of the invention. All questions regarding the scope of the invention may be resolved by referring to the appended claims.

Generally, the invention relates to systems and methods of intelligently regulating electronic messages. A system in accordance with the invention comprises an electronic message server with access to a database of information profiling legitimate electronic message usage. When an electronic message is received at the server, it is scrutinized relative to the information in the database. If the electronic message is found to be legitimate based upon this evaluation, it is delivered to the intended recipient. If, however, the electronic message appears on the basis of the evaluation to be the last in a series of unexpected usage or otherwise has characteristics inconsistent with the profile of legitimate electronic message usage, the electronic message may not be delivered and the sender and/or the postmaster at the site from which the electronic message originated is contacted.

An exemplary embodiment of a system and method for regulating electronic messages is described below. Specifically, a system and method for regulating e-mail is described below. The systems and methods are presented for exemplary purposes only and are not meant to limit the scope of the invention. Accordingly, those skilled in the art recognize that the invention applies to other types of electronic messages other than e-mail such as, for example, instant messages. Indeed, the present invention applies to any type of electronic message that can be said to originate from a particular Internet domain.

FIG. 1 is a high level diagram of an exemplary computer network for communicating e-mail. As shown, three e-mail servers 110, 112, and 114 are operable to communicate with one another over network 116, which may be for example, the Internet. E-mail servers 110, 112, and 114 communicate e-mails. E-mail servers 110, 112, and 114 may be operated by an ISP, a corporate computer department, or any other organization with a mail server connected to Internet 116. Each of mail servers 110, 112, and 114 are accessible by client stations 118 from which users send and receive e-mails and browse web pages. Client stations 118 may connect to mail servers via a local area network (LAN) 120, as shown in relation to server 110, or using a remote connection device 122 such as, for example, a modem, as is shown in connection with servers 112 and 114.

In the system of FIG. 1, e-mails are composed at client stations 118 and forwarded to one of e-mail servers 110, 112, and 114. E-mail servers 110, 112, and 114 communicate the e-mails over Internet 116 using SMTP and POP protocols. The e-mails are ultimately delivered at one of e-mail servers 110, 112, and 114. Client stations 118 use client e-mail software to access the e-mail from the servers.

E-mail servers 110, 112, and 114 comprise e-mail server software. Specifically, servers 110, 112, and 114 comprise simple mail transfer protocol (SMTP) and post office protocol (POP) software for receiving and routing e-mail. Those skilled in the art will recognize that while servers 110, 112, and 114 are depicted using a single machine in FIG. 1, the servers may comprise a plurality of computing machines, i.e. more than a single server machine may be employed to provide the functionality described herein as being provided by the server.

Client stations 118 comprise e-mail client software for communicating with e-mail servers 110, 112, and 114. Those skilled in the art will recognize that while client stations 118 are depicted as desk top computers, virtually any type of computing machine such as, for example, a PDA, a cell phone, or a lap top computer are suitable as an e-mail client.

E-mail servers 110, 112, and 114 as well as client stations 118 are generic computing systems. FIG. 2 is a block diagram of a generic computing system suitable for use in a system in accordance with the present invention. As shown, computing device 320 includes processing unit 322, system memory 324, and system bus 326 that couples various system components including system memory 324 to the processing unit 322. The system memory 324 might include read-only memory (ROM) and random access memory (RAM). The system might further include hard-drive 328, which provides storage for computer readable instructions, data structures, program modules and other data. A user may enter commands and information into the computer 320 through input devices such as a keyboard 340 and pointing device 342. A monitor 344 or other type of display device is also connected to the system for output. Communications device 343, which in one embodiment may be a modem, provides for communications over network 102. Processor 322 can be programmed with instructions to interact with other computing systems so as to perform the algorithms described below with reference to FIGS. 5A-C and 6. The instructions may be received from network 102 or stored in memory 324 and/or hard drive 328. Processor 322 may be loaded with any one of several computer operating systems such as Windows NT, Windows 2000, or Linux.

FIG. 3 is a diagram of the software components of e-mail servers 110, 112, and 114. As shown, servers 110, 112, and 114 comprise SMTP server software 310, POP server software 312, regulating software 314, and database 316. SMTP server software 310 operates according to known methods to route outgoing e-mails. POP server software 312 similarly operates according to know methods to route incoming e-mails. Regulating software 314 operates as described below in connection with FIGS. 5A-C and 6 to regulate e-mail flowing between servers. Regulating database software 316 implements the data structure described below with reference to FIG. 4 and stores the data used by regulating software 314.

FIG. 4 is a diagram depicting various entities and relationships established in a database system in accordance with an aspect of the present invention. As shown, a database, which may be maintained by server 110, 112, or 114, has stored therein data representing source categories 410. The source categories 410 represent a list of categories of sources from which e-mail may be received. These categories are referred to herein as “e-mail source categories” and are used in the evaluation of e-mails from un-registered sources. Typical e-mail source categories might include, for example, the following: large ISP—designating ISP's servicing a large number of users; medium ISP—designating ISP's servicing a medium number of users; small ISP—designating ISP's servicing a small number of users; .gov—designating sources in the .gov domain; .edu—designating sources in the .edu domain; and .com—designating sources in the .com domain. Of course, other e-mail source categories may be used depending upon the type of e-mail that it is desired to regulate.

Each source category has a set of target statistics 412 associated therewith. Target statistics might include, for example, a maximum e-mail volume that may be received in a prescribed period of time from a source in a particular source category. The database may prescribe, for example, that a maximum of 200,000 e-mails per hour may be received and processed from a source that is classified in the “.edu” source category. The target is statistics may further specify that the amount and types of e-mails that are allowed vary during different periods of the day. For example, during the off-peak hours of 12 AM to 5 AM, a larger number of e-mails may be accepted than during normal processing hours. Such a restriction may encourage postmasters to time-shift the delivery of unimportant e-mail. As explained in further detail below, the category statistics operate as benchmarks for the un-registered e-mail sources that fall within the particular category.

Each source category also has an e-mail profile 414 associated therewith. The target e-mail profile 414 identifies target characteristics for e-mails that are received from an un-registered source in a particular source category. For example, the target e-mail profile 414 for a particular source category might identify the maximum size for an e-mail, the maximum number of recipients, the types of attachments that might be included with the e-mail, the maximum number of hops that the e-mail may have taken prior to arriving at the mail server, and whether the source has agreed to be charged for delivery of e-mail. These characteristics are used as benchmarks to identify irregular mail activities.

A plurality of e-mail sources 416 may be associated with any one source category 410. For example, the “.com” source category may have a plurality of e-mail sources. Thus, sources such as, for example, bellsouth.com and hotmail.com would be related to the “.com” source category. For sources that have been registered, a designation of such is made in the database.

The database further comprises a set of statistics 418 for each e-mail source 416. The statistics are continuously updated to reflect each e-mail that is received from a particular source. For example, each time an e-mail is received in the system from a particular source such as, for example, bellsouth.com, the statistic holding the counter of e-mails received from that particular site is incremented. The statistics may also reflect the time and date that e-mails are received.

The database still further comprises a profile 420 for e-mails received from each registered source. Thus, the postmaster may, during the process of registration, define specific guidelines or a profile for e-mails from the registered source. The items that are part of the profile may be the same or similar to those used in connection with un-registered e-mail but the specific target values for the registered site may vary depending upon the postmaster's judgment and the particulars of the registered site.

Finally, the database may comprise target statistics 422 for each registered source. Accordingly, during the registration process, the postmaster may define specific target statistics for the registered site. The types of statistics that are required for registered sites may be the same or similar to those required for un-registered sources. However, the statistics for the registered source may be defined by the postmaster to reflect agreements that have been arranged with the registered source. For example, by agreement the communication of e-mails from the registered source may be skewed to be received during off-peak hours. Such an arrangement may be reflected in the statistics for the particular registered source. Furthermore, the statistics for a registered source may specify that the source has agreed to pay for services such as the delivery of e-mail.

The process of registering a source involves identifying the source, specifying target statistics for the source, and specifying an e-mail profile for e-mails from the source. This information is gathered from the postmaster, preferably through a series of interactive screens, and stored in the database.

FIG. 6 provides a flowchart of a process for registering an e-mail source. At step 610, the postmaster identifies the source that is to be registered. The source may be identified by domain name, IP address, or any other means that uniquely identifies and Internet domain. At step 612, the postmaster specifies the target statistics for the source. For example, the postmaster may specify that between the hours of 8 AM and 8 PM, the maximum number of e-mails that may be received from the source should be 100,000, while between the hours of 8 PM and 8 AM 200,000 e-mails may be received per hour. The postmaster may also specify that the source has agreed to pay for services such as delivery of e-mail. At step 614, the postmaster defines the target profile characteristics for e-mails from the registered source. For example, the postmaster may specify that e-mails from the registered source should not contain attachments or the attachments should be less than a prescribed file size.

FIG. 5A is a flowchart of a method for regulating e-mails in accordance with an aspect of the invention. As shown, at step 510, an e-mail is received at an e-mail server. For example, an e-mail may be received from smith@yahoo.com. At step 512, the regulating software 314 identifies the source of the e-mail. With respect to the exemplary e-mail from smith@yahoo.com, the source is identified as yahoo.com.

Those skilled in the art will recognize that an electronic message that has been forwarded numerous times may have multiple domains or “sources” listed in its header. Arguably, a single electronic message may be said to have “originated” from more than one source. Therefore, according to an aspect of the invention, at step 512 an electronic message may be designated as originating from more than one source. For example, a single electronic message may be said to have originated from the first or the last “hop” identified in the header information. An electronic message that is designated as having originated from more than one source is evaluated twice in the manner described below—once for each of the two sources.

At step 514, regulating software 314 updates the e-mail statistics 418 that are stored in database 316 to reflect receipt of the e-mail. For example, the statistic used to hold the counter of the number of e-mails received from yahoo.com is incremented.

At step 515, regulating software 314 determines if the source has been registered by the postmaster. If the source is determined to be registered as defined in the database entity 416, processing continues at step 517 as depicted in FIG. 5B. At step 517, the e-actual mail statistics 418 for the registered source of the e-mail are compared to the target statistics 422 for the registered source as determined by the postmaster. With respect to the example e-mail, assuming “yahoo.com” is a registered source, the statistics associated with “yahoo.com” are compared to the target statistics defined by the postmaster. At step 519, regulating software 414 determines whether the source statistics 418 fail to comply with the target statistics 422. For example, the volume of e-mails received over the course of the last hour from the source “yahoo.com” is compared with the target value for volume of e-mail specified by the postmaster for the registered source. If the value for the statistic of the source does not correspond to the target statistic as defined for the particular source, at step 521, the postmaster at the registered source is notified. For example, if the volume of e-mails received from “yahoo.com” is determined to be outside the benchmark specified by the postmaster for the source, an e-mail is sent to the postmaster of yahoo.com apprising him or her of the situation.

At step 523, regulating software 314 retrieves the profile of characteristics for e-mails 420 received from the particular registered source. At step 525, the characteristics of the e-mail under consideration are compared to the e-mail profile 420 defined by the postmaster for the registered source. For example, the characteristics for the e-mail from smith@yahoo.com are compared to the e-mail profile characteristics specified by the postmaster for the registered source. For example, the comparison might include determining if the number of recipients exceeds the limit stored in the e-mail profile characteristics.

If at step 527, the characteristics of the e-mail under consideration conflict with the profile defined for the registered source, at step 529, the sender and the postmaster of the source web site are notified. If at step 527, there is no discrepancy between the e-mail and the profile 420, the e-mail is delivered to the intended recipient as specified at step 531.

Referring back to FIG. 5A, if at step 515, regulating software 314 determines that the source has not been registered, processing continues at step 516 as depicted in FIG. 5C. At step 516, regulating software 314 identifies the source category with which the source of the e-mail is related. With respect to the example, the source of the e-mail, “yahoo.com,” is identified as being associated with the “.com” source category. It should be noted that sources could also be identified by way of an IP address.

At step 518, the e-mail statistics 418 for the source of the e-mail are compared to the target statistics 412 for the source category. With respect to the example e-mail, the statistics associated with “yahoo.com” are compared to the target statistics associated with “.com” source category. At step 520, regulating software 414 determines whether the source statistics fail to comply with the target statistics for the associated source category. For example, the volume of e-mails received over the course of the last hour from the source “yahoo.com” are compared with the target value for volume of e-mail associated with the source category “.com.” If the value for the statistic of the source does not correspond to the target statistic for the associated source category, at step 522, the postmaster at the source is notified. For example, if the volume of e-mails received from “yahoo.com” is determined to be outside the benchmark set for the “.com” source category, an e-mail is sent to the postmaster of yahoo.com apprising him or her of the situation.

At step 524, regulating software 314 retrieves the profile of characteristics for e-mails received from the relevant source category. With respect to the example, the e-mail profile 414 is retrieved for the “.com” source category. At step 526, the characteristics of the e-mail under consideration are compared to the e-mail profile. For example, the characteristics for the e-mail from smith@yahoo.com are compared to the e-mail profile characteristics stored in relation to the “.com” source category. The comparison might include determining if the number of recipients exceeds the limit stored in the e-mail profile characteristics.

If at step 528, the characteristics of the e-mail under consideration conflict with the profile associated with the source category, at step 530, the sender and the postmaster of the source web site are notified.

At step 532, the e-mail is evaluated against a known set of viruses. If a virus is detected at step 534, the e-mail is not delivered and the postmaster and/or administrator are notified at step 536. If, however, no viruses are detected, at step 538, the e-mail is delivered to the intended recipient.

It should be noted that in alternative embodiments, if at step 520, the source statistics did not comply with the target statistics or at step 528 the e-mail characteristics did not comply with the e-mail profile, the e-mail might not be delivered to the intended recipient but returned to user from which the e-mail was forwarded.

Finally, at step 540, any counters that are used in connection with the collection of statistics for the source and which need to be reset, are reset. For example, if one of the statistics that is collected for a source is the number of e-mails received during the current hour and the hour has expired, the counter is reset at step 540.

Thus, systems and methods for regulating the flow of electronic messages have been disclosed. These novel systems and methods allow postmasters and administrators to place limits on the type and amounts of electronic messages that are accepted into the system. This will help postmasters and administrators slow the influx of SPAM and save resources for legitimate uses.

Those skilled in the art understand that computer readable instructions for implementing the above described processes, such as those described with reference to FIG. 5, can be generated and stored on one of a plurality of computer readable media such as a magnetic disk or CD-ROM. Further, a computer such as that described with reference to FIG. 2 may be arranged with other similarly equipped computers in a network, and each computer may be loaded with computer readable instructions for performing the above described processes. Specifically, referring to FIG. 2, microprocessor 322 may be programmed to operate in accordance with the above-described processes.

While the invention has been described and illustrated with reference to specific embodiments, those skilled in the art will recognize that modification and variations may be made without departing from the principles of the invention as described above and set forth in the following claims. For example, while the invention has been described as being used to regulate the in-flow of e-mail at a mail server, the invention might also be used to regulate the out-flow of e-mail at a web server. Furthermore, the invention may be employed to regulate the flow of all types of electronic messages, including instant messaging. Accordingly, reference should be made to the appended claims as indicating the scope of the invention. 

1. A method for regulating electronic messages comprising: receiving, by a server, a first input that specifies an identifier that is unique to an electronic message source to be registered; recording, by the server, profile information for the electronic message source, the profile information comprising an indication whether the electronic message source has agreed to pay for an e-mail usage report; receiving a second input specifying target statistics for the electronic message source to be registered, wherein the target statistics operate as benchmarks for determining whether a plurality of electronic messages received from the electronic message source to be registered are acceptable, wherein the second input specifies the target statistics based on an agreement to pay for delivery of the plurality of electronic messages from the electronic message source and on the agreement which further specifies a receipt of a number electronic messages from the electronic message source during off-peak hours wherein the plurality of electronic messages comprise email messages and instant messages; registering the electronic message source and storing information identifying the target statistics for the electronic message source that has been registered; receiving a particular electronic message; if a source of the particular electronic message is the electronic message source that has been registered: updating, by the server, statistics related to the electronic message source that has been registered, based on the particular electronic message received from the electronic message source that has been registered; comparing the statistics updated to the target statistics; and taking a remedial action with respect to the particular electronic messages received if the statistics updated for the electronic message source that has been registered conflict with the target statistics; and if a source of the particular electronic message has not been registered: identifying a source category to which the source of the particular electronic message source is related; accessing source category target statistics associated with the source category, wherein the source category target statistics specify an acceptable volume of emails; comparing the statistics updated for the source of the particular electronic message to the source category target statistics; and taking a second remedial action if the statistics updated for the source of the particular electronic message source conflict with the source category target statistics.
 2. The method of claim 1, wherein receiving the first input identifying the electronic message source to be registered comprises identifying the electronic message source by means that uniquely identify an internet domain.
 3. The method of claim 1, wherein the first input identifies the electronic message source by at least one of a domain name and an Internet Protocol address.
 4. The method of claim 1, wherein receiving the second input specifies a limit on a number of the electronic messages received from the electronic message source within a period.
 5. The method of claim 1, further comprising receiving a third input specifying target profile characteristics for an electronic message of the plurality of electronic messages received from the electronic message source.
 6. The method of claim 5, wherein the target profile characteristics relate to a size of an electronic message received from the electronic message source, a type of attachment for the electronic message source, a number of recipients for the electronic message received from the electronic message source, and a number of hops that an electronic message received from the electronic message source had taken.
 7. The method of claim 6, wherein the third input specifies a size limit for the electronic message received from the electronic message source.
 8. The method of claim 6, wherein the third input specifies types of attachments that are acceptable for an electronic message received from the electronic message source.
 9. The method of claim 6, wherein the third input specifies a limit of a number of recipients for an electronic message received from the electronic message source.
 10. The method of claim 6, wherein the third input specifies a limit on a number of hops that an electronic message received from the electronic message source had taken. 